Methods and systems for managing an electronic calendar

ABSTRACT

Methods and systems for managing an electronic calendar are described. One exemplary method includes displaying a calendar on a display device, the calendar having at least one time range, and displaying an invitation, before it is accepted, on the calendar in the at least one time range with other events which are already accepted. Another exemplary method includes displaying a calendar on a display device and displaying a list of user-selectable calendars comprising an invitation calendar which presents invitations which have not yet been accepted or declined on the invitation calendar. Other methods are described, and machine readable media and systems are also described.

CLAIM OF PRIORITY

This application is a continuation of and claims the benefit of priorityto U.S. patent application Ser. No. 11/499,406, filed Aug. 4, 2006,which is hereby incorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

The present inventions relate to methods and systems for managing anelectronic calendar.

An electronic calendar is typically implemented on a data processingsystem, such as a general purpose computer system or a personal digitalassistant (PDA) or a cellular telephone or a media player (e.g. an iPod)or other types of devices. These electronic calendars typically allow auser to display different time intervals or time ranges within acalendar. For example, an electronic calendar will typically allow auser to display at least a portion of a day, a full day, a portion of aweek or a full week, several weeks, or a month, or a plurality ofmonths, or even multiple years. The electronic calendars furthertypically include user interfaces for allowing a user to move betweenthe different time durations or time ranges and to enter events andreminders onto the calendar. The events and/or reminders typicallyinclude some text specifying the event as well as data specifying theduration in time of the event and other information. A user cantypically save these reminders or events at a particular time on thecalendar and then later retrieve the information from the calendar tosee what events are upcoming, to plan for events, etc.

Oftentimes, an event may require several people to attend the event,such as a meeting or a party, etc. In these circumstances, the creatorof the event on the calendar will typically send out an invitation tothose being invited to or requested to attend the event. Prior dataprocessing systems allow a user to create an event on a calendar andthen cause an electronic message to be sent out to those being invitedor requested to attend the event. The message may be sent by anelectronic message, such as email, or some other type of notificationabout the event. These invitations are received by attendees or othersrequired to attend in an email form which does not display theinvitation in a calendar or in the context of a calendar with otherevents listed on the calendar which have already been accepted. Hence, auser cannot see the date and time of the invitation in the context ofother events already on the user's calendar. Moreover, prior systems andmethods do not include a calendar which is devoted to showinginvitations which have not yet been accepted.

SUMMARY OF THE DESCRIPTION

Methods and systems for managing electronic calendars are describedherein. One exemplary method for managing an electronic calendarincludes displaying a calendar on a display device, the calendar havingat least one time range, and displaying an invitation, before it isaccepted, on the calendar in the at least one time range. Typically, theinvitation relates to an event having a time in a time duration, and theinvitation is displayed at that time on the user's calendar with anindication of the time duration on the user's calendar. In certainembodiments, the method may further include receiving a user input todisplay the invitation before it is accepted on the calendar along withother events, which are already accepted, on the user's calendar. Inaddition, the method may further include receiving a notification of theinvitation before it is displayed on the calendar, and displaying a userinterface to allow a user to accept or decline the invitation. Incertain embodiments, the user interface may comprise an accept icon or adecline icon or both displayed on the invitation itself on the user'scalendar. In certain implementations, the method may also includedisplaying a list of user-selectable calendars which include aninvitation calendar which presents invitations which have not beenaccepted or declined and wherein accepting the invitation causes theinvitation to be removed from the invitation calendar and causes theinvitation to be displayed on the user's calendar in a form to show ithas been accepted. In at least certain embodiments of one or more ofthese methods, the invitation, as it is displayed on the user's calendarbefore it is accepted, is displayed in a manner to differentiate itselffrom other events which have already been accepted. For example, theinvitation may appear with a coupon-like perimeter or frame and may beshown in a color which is different than the color of other events whichhave already been accepted in the user's calendar.

Another aspect of the present inventions relates to the use of aninvitation calendar which may be part of a user-selectable list ofcalendars. One exemplary method which uses an invitation calendarincludes displaying a calendar on a display device, the calendar havingat least one time range, and displaying a list of user-selectablecalendars including an invitation calendar which presents invitationswhich have not yet been accepted on the invitation calendar. This methodmay also display, for each user-selectable calendar in the list, a userinterface to cause events from a corresponding calendar to be displayedor not displayed on the calendar. In this example, when the userinterface for the invitation calendar is set to cause invitations fromthe invitation calendar to be displayed, then invitations are displayedon the user's calendar before an invitation is accepted, and when theuser interface for the invitation calendar is set to cause invitationsfrom the invitation calendar to be not displayed, then the invitationsare not displayed. This method may further include receiving anotification of an invitation and displaying an alert or otherinformation with respect to the invitation, and the method may furtherinclude displaying a user interface to allow a user to accept theinvitation. The invitations, when displayed on the calendar before beingaccepted, may be visually distinguishable from other events from othercalendars in the list of user-selectable calendars.

One or more methods described herein by be performed by a dataprocessing system, such as a general purpose computer system, a PDA, acellular telephone, a media player, etc. These devices may use one ormore computer programs to perform these methods and they may includemachine readable media containing those computer programs.

The methods and/or computer programs of any one of these embodiments maybe compliant with standards for calendaring applications, such as iCaland vCal, and may allow for the importation of data from otherapplications such as Entourage, or other calendaring programs.

In addition, in at least certain embodiments, the methods or systemsdescribed herein may enable copy and paste operations with otherapplications, and may enable drag and drop manipulations or the use of aspell checker, or the integration with email applications and addressbook applications for management of personal information. Furthermore,in at least certain embodiments, the methods and systems describedherein may also permit users to publish their calendars to others (e.g.publish their calendar through the use of the Internet) and may alsoallow a user to subscribe to other calendars, thereby coordinating ormanaging events of one user with those of another.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 shows an exemplary data processing system which may be used in atleast certain embodiments described herein.

FIG. 2 is a flow chart which depicts an exemplary embodiment describedherein.

FIGS. 3A, 3B, 3C, 3D, and 3E show examples of a user interface whichincludes a list of selectable calendars.

FIG. 3F shows another example of a user interface which includes aplurality of user-selectable calendars in a list, each of which may betoggled on or off and thereby shown or not shown on the user's calendarwithin the calendar window.

FIG. 4A shows a flow chart illustrating another exemplary methoddescribed herein.

FIG. 4B is another flow chart showing another exemplary embodiment ofthe methods described herein.

FIGS. 5A, 5B, 5C, 5D, 5E, and 5F illustrate exemplary user interfacesfor creating an event or invitation.

FIGS. 6A, 6B, and 6C illustrate exemplary user interfaces showing howinvitations may be received and displayed within a user's calendar evenbefore the invitation is accepted.

DETAILED DESCRIPTION

The subject invention will be described with reference to numerousdetails set forth below, and the accompanying drawings will illustratethe invention. The following description and drawings are illustrativeof the invention and are not to be construed as limiting the invention.Numerous specific details are described to provide a thoroughunderstanding of the present invention. However, in certain instances,well known or conventional details are not described in order to notunnecessarily obscure the present invention in detail.

The present description includes material protected by copyrights, suchas illustrations of graphical user interface images. The owners of thecopyrights, including the assignee of the present invention, herebyreserve their rights, including copyright, in these materials. Thecopyright owner has no objection to the facsimile reproduction by anyoneof the patent document or the patent disclosure, as it appears in thePatent and Trademark Office file or records, but otherwise reserves allcopyrights whatsoever. Copyright Apple Computer, Inc. 2006.

FIG. 1 shows one example of a typical computer system which may be usedwith the present invention. Note that while FIG. 1 illustrates variouscomponents of a computer system, it is not intended to represent anyparticular architecture or manner of interconnecting the components assuch details are not germane to the present invention. It will also beappreciated that PDAs, cellular telephones, media players (e.g. aniPod), devices which combine aspects or functions of these devices (e.g.a media player combined with a PDA and a cellular telephone in onedevice), network computers, an embedded processing device within anotherdevice, and other data processing systems which have fewer components orperhaps more components may also be used to implement one or moreembodiments of the present inventions. The computer system of FIG. 1may, for example, be a Macintosh computer from Apple Computer, Inc.

As shown in FIG. 1, the computer system 101, which is a form of a dataprocessing system, includes a bus 102 which is coupled to amicroprocessor(s) 103 and a ROM (Read Only Memory) 107 and volatile RAM105 and a non-volatile memory 106. The microprocessor 103 may be amicroprocessor or set of microprocessors from Intel or a G3 or G4microprocessor from Motorola, Inc. or one or more G5 microprocessorsfrom IBM. The bus 102 interconnects these various components togetherand also interconnects these components 103, 107, 105, and 106 to adisplay controller and display device 104 and to peripheral devices suchas input/output (110) devices which may be mice, keyboards, modems,network interfaces, printers and other devices which are well known inthe art. Typically, the input/output devices 109 are coupled to thesystem through input/output controllers 108. The volatile RAM (RandomAccess Memory) 105 is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. The mass storage 106 is typically a magnetic hard drive or amagnetic optical drive or an optical drive or a DVD RAM or other typesof memory systems which maintain data (e.g. large amounts of data) evenafter power is removed from the system. Typically, the mass storage 106will also be a random access memory although this is not required. WhileFIG. 1 shows that the mass storage 106 is a local device coupleddirectly to the rest of the components in the data processing system, itwill be appreciated that the present invention may utilize anon-volatile memory which is remote from the system, such as a networkstorage device which is coupled to the data processing system through anetwork interface such as a modem or Ethernet interface. The bus 102 mayinclude one or more buses connected to each other through variousbridges, controllers and/or adapters as is well known in the art. In oneembodiment the I/O controller 108 includes a USB (Universal Serial Bus)adapter for controlling USB peripherals and an IEEE 1394 controller forIEEE 1394 compliant peripherals.

It will be apparent from this description that aspects of the presentinvention may be embodied, at least in part, in software. That is, thetechniques may be carried out in a computer system or other dataprocessing system in response to its processor, such as amicroprocessor, executing sequences of instructions contained in amemory, such as ROM 107, RAM 105, mass storage 106 or a remote storagedevice. In various embodiments, hardwired circuitry may be used incombination with software instructions to implement the presentinvention. Thus, the techniques are not limited to any specificcombination of hardware circuitry and software nor to any particularsource for the instructions executed by the data processing system. Inaddition, throughout this description, various functions and operationsare described as being performed by or caused by software code tosimplify description. However, those skilled in the art will recognizewhat is meant by such expressions is that the functions result fromexecution of the code by a processor, such as the microprocessor 103.

One example of a computer program which may implement one or moremethods described herein is the computer program called iCal from AppleComputer, Inc. of Cupertino, Calif. Further information about thiscomputer program is also provided by published U.S. Patent ApplicationNo. US2004/0044646, which published application is hereby incorporatedherein by reference.

FIG. 2 shows a flow chart illustrating one or more exemplary embodimentsof methods of the present inventions. The method of FIG. 2 begins inoperation 201 in which a list of displayable calendars with selectioncommands is displayed. This list may be displayed within a calendarwindow and the selection commands may be displayed adjacent to eachcorresponding calendar which the command controls. Each command isselectable by a user to display or not display events from a particularcalendar, thereby causing events to appear or not appear within the timerange, such as a week view of a user's calendar. FIG. 3A shows anexample of a user interface for a calendar application. The calendarapplication causes the display of a calendar window 301 which includes aview 302 of a user's calendar. In the example of FIG. 3A, the view is aweek view, but it will be appreciated that alternative views may show aday view or a month view or other types of views. The view 302 shows anevent 303 from the user's work calendar 309 shown in the list ofdisplayable calendars 305. The view 302 also shows an event 304 from theuser's home calendar 307, also shown in the list of selectable calendars305. The list 305 also includes an invitation calendar 311. Each of thethree calendars shown in the list 305 includes a respective selectioncommand. In particular, the home calendar 307 includes a selectioncommand 313, and the work calendar 309 includes a selection command 315,and the invitation calendar 311 includes a selection command 317. Eachof these selection commands may be independently selected or notselected by the user, thereby causing events from the correspondingcalendar to appear or not appear within the view 302 of the user'scalendar. In the example shown in FIG. 3A, the user (or alternatively,software under default or other setting), has selected for displayevents from both the home calendar 307 and events from the work calendar309 and thus check marks 316 and 318 appear within the correspondingselection commands 313 and 315. The selection commands may be activatedin a variety of ways, including cursor inputs or keyboard inputs orspeech inputs to the data processing system. For example, a user mayposition a cursor, as controlled by a mouse or other cursor controldevice, over the corresponding selection command and thereafter pressinga button, such as a mouse's button, to select the command or deselectthe command. Also as shown in FIG. 3A, the invitation calendar has notbeen selected and thus there is no check mark in the selection command317; hence, invitations from the invitation calendar which have not beenaccepted will not be displayed in the view 302. A notification 319 isalso displayed within the window 301. This notification indicates thatthere is an unread invitation and tells the user to select theinvitation calendar to see the unread invitation.

In response to the notification, the user may select the selectioncommand 317 to cause invitations from the invitation calendar 311 toappear in the view 302. Alternatively, in response to an invitation, thesystem may automatically cause the selection of the selection command317 to thereby cause unaccepted invitations to appear in the view 302 inthe user's calendar. Referring back to FIG. 2, operation 203 involvesreceiving an input to cause the display of invitations from aninvitation calendar onto a calendar displayed to a user. In response, inoperation 205, invitations from the invitation calendar are displayed ona view of the user's calendar on a display device. FIG. 3B shows anexample of such a view in which an unaccepted invitation from theinvitation calendar is displayed in the view 302. A check mark 317Ashows that the user has, or the system has, caused an input, which wasreceived in operation 203, to thereby cause invitations to appear in theview 302. As shown in FIG. 3B, the home calendar and the work calendarhave also been selected in the list 305 and hence events from both ofthose calendars are also displayed in the view 302 as shown in FIG. 3B.In particular, event 303 from the work calendar, event 304 from the homecalendar, and the invitation 321 from the invitation calendar 311 areall concurrently displayed in the view 302. Events 303 and 304 aredisplayed in a fashion showing that they have been accepted, while theinvitation 321 is displayed in a manner to show that it has not yet beenaccepted or declined. This is shown by the visual indicator 323. Thereare numerous alternative ways to show that the invitation 321 has notyet been accepted or declined in the view 302. For example, theunaccepted invitation may flash or be displayed with a coupon-likeperimeter or displayed with text indicating it is not yet accepted, ordisplayed with “accept” and “reject” icons adjacent to the invitation onthe view 302, etc. FIG. 3F shows a particular embodiment in which theinvitations 365 and 367, which have not yet been accepted, are displayedin a view of a calendar while other events which have been accepted,such as event 366, is displayed differently. FIG. 6B shows an example inwhich an invitation which has not yet been accepted, such as invitation609A, includes “accept” and “decline” icons which may also be used todifferentiate an unaccepted invitation from other events which have beenaccepted. A user may decide, while viewing the user interface shown inFIG. 3B, to view only invitations from the invitation calendar, and thisresult is shown in FIG. 3E in which only the invitation calendar hasbeen selected through the selection command 317, while the otherselection commands 313 and 315 have been deselected, such that eventsfrom the home calendar and the work calendar do not appear in the view302 shown in FIG. 3E. Hence, the list of selectable calendars 305 allowsa user to toggle calendars on or off independently to focus on aparticular calendar, although it will be appreciated that the userinterface shown in FIG. 3B gives the user the ability to see theinvitation which has not yet been accepted relative to other events inadditional calendars beyond the invitation calendar. It will beunderstood that there may be a plurality of invitations which have notyet been accepted which are shown on the invitation calendar, and anexample of this is shown in FIG. 3F which includes two unacceptedinvitations 365 and 367 along with other events from selected calendarsas shown in FIG. 3F. It will be appreciated that a user may remove theinvitations from view 302 shown in FIG. 3B by deselecting the invitationcalendar 311 in the list 305, and this will return the view to the stateit was in FIG. 3A. This is also shown as operations 207 and 209 of FIG.2.

The user may accept or decline an invitation by using one of a varietyof different user interfaces as further described herein. FIGS. 3C and3D show an example of the user interface of one embodiment after aninvitation has been accepted. It can be seen from FIG. 3C that the view302 now includes the event 321 which is an accepted invitation, and itis displayed as other events are also displayed which have beenaccepted. Thus, the appearance of the event 321 is similar to theappearance of the event 303. Also note that events from only the workcalendar are now shown in the view 302, while events from the homecalendar are not shown (and hence the event 304 is not shown in the view302 of FIG. 3C). FIG. 3D shows the invitation calendar 311 only in theview 302. There are no invitations shown in the view 302 of FIG. 3Dbecause the invitation related to event 321 has been accepted and henceit has been removed from the invitation calendar as shown in the view302 of FIG. 3D. In certain embodiments, the invitation calendar showsonly invitations, such as invitations which have not yet been accepted.

FIG. 3F shows one example of a user interface according to oneembodiment of the present inventions. This user interface includes acalendar window 351 shown on a desktop 353. A dock 357 is also shown onthe desktop 353. The dock includes an icon 371 representing the calendarapplication which is running and causing the display of the calendarwindow 351. The dock also includes a notification icon 373 whichindicates that the system has received one notification relating to aninvitation. The user interface also includes a pull-down menu region355. The calendar program window 351 includes a user interface 369 forselecting a time range, such as a week or day or month range for displayof events within the view 360 of the user's calendar. As shown in FIG.3F, the week range has been selected from the user interface 369,causing a week view to appear in the view 360. Numerous events fromthree different calendars (a work calendar, a home calendar, and aninvitations calendar) are shown within the view 360. For example, event366 from the home calendar is shown with several events from the workcalendar. In addition, two invitations 365 and 367 are also shown in theview 360 concurrently with the other events from the other calendars. Aswith the example shown in FIG. 3A, the calendars may be selectivelyturned on or off, thereby displaying or not displaying events from aselected calendar. As can be seen from FIG. 3F, the invitations calendar363 has been selected for display, causing the invitations 365 and 367to appear without a particular color which is related to the othercalendars and to appear with a coupon-like perimeter, indicating to theuser that these events are invitations which have not yet been accepted.A notifications portion of the calendar program window 351 shows twonotifications 361 and 362. The notification 361 has been expanded toshow details about this particular notification which relates to theinvitation 367 shown in a particular time on Thursday, May 11. Note thatthe invitations are shown at the particular time of the invitation onthe view 360 and that the duration of the invitation is also shown bythe area that the invitation spans on the view 360. This is similar tohow the area of the events which have been accepted, such as event 366,also indicates the duration of the event. The notification 361 includesan “accept” icon and a “decline” icon for accepting or declining theinvitation 367. In an alternative embodiment, these icons may be shownonly when the invitation 367 is within the view 360 or in addition tothe invitation 367 on the view 360.

FIG. 4A is a flow chart indicating an exemplary method according to oneaspect of the present inventions. In operation 401, a calendar isdisplayed to a user. Then in operation 403, an invitation to an eventwhich has not yet been accepted and which has not yet been declined, isreceived. This invitation is displayed, in operation 405, before it isaccepted or declined. It is displayed, in operation 405, on the calendarat its date and time and may include an indication of the duration ofthe event related to the invitation. Examples of user interfaces relatedto this method of FIG. 4A have been provided above, including, forexample, the user interface in FIG. 3B and the user interface shown inFIG. 3F in which invitations are displayed before they are accepted ordeclined on the user's calendar at the date and time of the invitation.

FIG. 4B shows a more detailed method than the method of FIG. 4A, andthis more detailed method is yet another exemplary embodiment accordingto at least one aspect of the present inventions. Examples of userinterfaces which illustrate at least portions of this method have beenprovided herein, including, for example, FIGS. 3A, 3B, 3F, and otherfigures. In operation 411, the data processing system displays acalendar to a user. In operation 413, a notification of an invitation isreceived, and the data processing system presents a notice to the userabout the invitation. It will be appreciated that in certainembodiments, the sequence of operations 413 and 411 may be reversed. Forexample, the calendar may be displayed in operation 411 after receivingthe notification 413, and this may occur automatically in response tothe notification. It will be also appreciated that various othersequences for other operations in the methods shown in FIG. 4B may beutilized by at least certain embodiments of the present inventions. Inoperation 415, it is determined whether or not invitations have beenselected to be displayed in a view of a user's calendar. In oneembodiment, this may involve determining whether or not a selectioncommand, such as selection command 317, has been selected, either by theuser or by the system. If it has not been selected, then operation 417follows, and if it has been selected, then operation 419 follows asshown in FIG. 4B. In operation 417, the data processing system receivesa user's command (or a system input or a programmatic input) to show theinvitations, and in response, the invitations are shown on the user'scalendar at the date and time of the invitation in a selected date rangeon the calendar. If the invitations had been selected, as determined inoperation 415, then operation 419 follows in which the invitation isdisplayed or otherwise presented on the user's calendar. In operation421, user interface commands are displayed to allow the user to acceptor decline the invitation. The user's input (or input from the system ora software program) is received in operation 423, which input indicateswhether or not to accept or decline the invitation. If the invitation isaccepted, then operation 425 follows, and if the invitation is declined,then operation 427 follows. In operation 425, the invitation isdisplayed as accepted and thus the event appears as other acceptedevents appear on the user's calendar. Optionally, the event whichconstitutes the invitation is also removed from the invitation calendaror is shown as accepted on the invitation calendar. In operation 427, ifthe operation is declined, then it is removed from the user's calendarand optionally shown as declined on the invitation calendar. In anotherembodiment, the declined event may also be removed from the invitationcalendar in addition to removing it from the user's calendar.

Additional examples of embodiments of user interfaces will now beprovided by FIGS. 5A-5F and FIGS. 6A-6C. FIGS. 5A-5F show examples ofhow events are created within a calendar and how invitations may becreated from the sender's side of an invitation. FIG. 5A shows anexample of a calendar application window 501 which includes a view 503of a user's calendar. This view may be selected to be at one of aplurality of different time ranges, such as a day range or a week rangeor a month range or a year range, as determined by the range selector507. In the particular example shown in FIG. 5A, an input has beenreceived which instructed the system to display events within a weekrange in the view 503. The calendar application window 501 also includesa list 505 of selectable calendars, which in this case have all beenselected for having their events displayed within the view 503. The view503 includes an event 509, which has already been scheduled, and anevent 511, which is currently being scheduled as shown in the example ofFIG. 5A. The cursor 513 is being used to select the duration of theevent 511 as shown in FIG. 5A. After the duration has been selected, adialog window 514 is displayed as shown in FIG. 5B, allowing user inputinto three fields 516, 518, and 520. The field 516 of FIG. 5B allows theuser or the system to enter text which represents the name of the eventor other information. The field 518 allows the user or the system toenter attendees; in certain embodiments, the user or the system maymerely enter the first part of an attendee's name and the system willsearch through contact databases or address databases for that person'sname and may include contact information, such as an email address or aphone number or other contact information which can be used to alert theattendees of the events/invitation as shown below. In the case of theexample shown in FIGS. 5B and 5C, there will be no attendees, and thusthe field 518 remains blank in both FIGS. 5C and 5B. Similarly, thelocation field 520 also remains blank. After the user has entered textinto field 516 as shown in FIG. 5C, the user can then complete the entryof data for the event 511 by selecting the “done” button 522 bypositioning a cursor 524 over the done button; in other embodiments,other inputs may be used to indicate that the user has completed entryof information with respect to an event. For example, the user may pressa key, or button, such as a return button on a keyboard.

FIGS. 5D, 5E, and 5F show an example of user interfaces for creating anevent and an invitation at the sender's side of the invitation. Thesequence of user interfaces shown in FIGS. 5D, 5E, and 5F follow thesequence of user interfaces shown in FIGS. 5A, 5B, and 5C. Hence, theevent 511 has turned into event 511A, as shown in FIG. 5D, because theuser has completed entry of information in connection with that eventwhich now appears in the view 503. The user, as shown in FIG. 5D, hasbegun creating a new event 531 which will also become an invitationbecause the event has two attendees. As shown in FIG. 5D, the user hasentered a name for the event/invitation in a field 535 within the window533 which accepts input for the event/invitation. The user has alsoentered a portion of one of the attendees' names within the field 537which specifies the attendees. In response, the system returns a list ofnames which match the text entered into field 537. In particular, thesystem returns a list 539 from which the user can select one or morenames for entry into the field 537. In the particular example shown inFIG. 5D, the attendees are specified by name and by email address andnotifications about the invitation will be sent to the attendees byemail. In alternative embodiments, other messaging techniques, such astelephone contacts, instant messaging addresses or contacts, etc. may bealternatively used or used in addition to email addresses. After aselection of the attendees as shown in FIG. 5D, the window 533 is readyto receive a location input into field 541 as shown in FIG. 5E. The useror the system then enters a location in the field 541 as shown in FIG.5F and at this point the invitation is ready to be sent, and the event'sdata entry will be completed after the user selects the “send” button543 as shown in FIG. 5F. Selecting that button will then cause the eventto be displayed as event 531 on the sender's calendar and will alsocause a notification, in this case by email, to be sent to the twoattendees listed in field 537. In the embodiment discussed relative toFIGS. 6A-6C on the attendee's side, these emails are used to provide anotification from an email program to the calendaring program at theattendee's side so that the notification can be received directly withinthe calendaring window rather than merely in an email applicationwindow.

FIGS. 6A, 6B, and 6C illustrate the receipt of the invitation at theattendee's side of an invitation. In this particular example, theinvitation created and sent from FIGS. 5D, 5E, and 5F is received at theattendee's side as shown in FIGS. 6A, 6B, and 6C. The attendee is usinga data processing system which displays a calendar application window601 which includes a view 603 showing a week time range in the view 603as determined by the interface control 607 in which the week time rangeis selected. The calendar application window 601 also includes a list ofselectable calendars which includes an invitation calendar 607 shown inthe list 605. As can be seen from FIG. 6A, all of the calendars havebeen selected to show their events within the view 603. For example, theinvitations calendar 607 has been selected to show its events, which inthis case are unaccepted invitations as shown by the selection command608, which includes a check mark in the selection command 608. Thecalendar application window 601 also shows the invitation 609 and anotification 611 within the window. The invitation 609 is shown in theview 603 in a form to indicate that it has not yet been accepted ordeclined. In the example shown in FIGS. 6A and 6B, this form includes acoupon-like perimeter which includes a dotted or dashed line. Further,the invitation is shown without any of the colors used to indicate otherevents for other calendars. For example, all events from the homecalendar may be shown in red while events from the work calendar may beshown in green, etc. As noted above, other types of indicators mayalternatively be used or used in addition to those mentioned to showthat the event is an invitation which has not yet been accepted. Thenotification 611 results from the email sent from the sender's system asa result of selecting the send button 543 shown in FIG. 5F.Alternatively, the notification could arrive from an instant messagingmessage or other electronic messages or even an automated phone systemcaused to make a phone call by selecting the send button 543 which, inturn, is received automatically by a recipient's data processing systemwhich in turn converts this into a notification, such as notification611. Information within the notification 611 includes the name of theevent 619 and the sender of the event or invitation 617. In addition,the invitation includes an “accept” icon 615 which may be used to acceptthe invitation, and a “decline” icon 613 which may be used to declinethe invitation. FIG. 6B shows an alternative embodiment in which acceptand decline icons also appear within the invitation itself on thecalendar, such as within the view 603 as shown in FIG. 6B. Inparticular, a decline icon 613A and an accept icon 615A are shown withinthe invitation 609A as shown in the view 603. The user can accept theinvitation by selecting either icon 615 or 615A shown in FIG. 6B, andcan decline the invitation by selecting either icon 613 or 613A.Accepting the invitation causes the invitation to be removed, in atleast certain embodiments, from the invitation calendar 607, and causesthe event to be displayed as a normal event rather than an invitation asshown in FIG. 6C, in which the event 609C now becomes an event withinthe home calendar and assumes the color of events (e.g. red) of eventswithin the home calendar.

In the foregoing specification, the invention has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope of the invention as set forth in thefollowing claims. The specification and drawings are, accordingly, to beregarded in an illustrative sense rather than a restrictive sense.

What is claimed is:
 1. A method comprising: at a computing device with adisplay device and one or more input devices: displaying, on the displaydevice, a calendar window that comprises concurrently displaying: acalendar view corresponding to a time range, wherein: the calendar viewincludes graphical representations of a plurality of events that includea first graphical representation of a first event that has a size thatrepresents the duration of the first event and a second graphicalrepresentation of a second event that has a size that represents theduration of the second event; the calendar view includes graphicalrepresentations of a plurality of event invitations that include a firstgraphical representation of a first event invitation that has a sizethat represents the duration of an event that corresponds to the firstevent invitation and a second graphical representation of a second eventinvitation that has a size that represents the duration of an event thatcorresponds to the second event invitation; and the graphicalrepresentations of the plurality of event invitations share a visualproperty that visually distinguishes the graphical representations ofevent invitations from graphical representations of events; and anotification region, wherein: the notification region includes a firstnotification corresponding to the first event invitation and a secondnotification corresponding to the second event invitation; the firstnotification corresponding to the first event invitation includes anaccept icon for accepting the first event invitation and a decline iconfor declining the first event invitation; and while displaying thecalendar view: receiving, via the one or more input devices, an inputthat corresponds to selection of the accept icon in the firstnotification; and in response to receiving the input, updating thecalendar view on the display by changing the visual property of thefirst graphical representation of the first event invitation to indicatethat the event invitation has been accepted.
 2. The method of claim 1wherein the second notification includes an accept icon for acceptingthe second event invitation and a decline icon for declining the secondevent invitation; and while displaying the calendar view: receiving, viathe one or more input devices, a second input that corresponds toselection of the decline icon in the second event invitation; and inresponse to receiving the second input, updating the calendar view onthe display by removing the second graphical representation of thesecond event invitation to indicate that the event invitation has beendeclined.
 3. The method of claim 1, further comprising: receiving viathe one or more input devices a second input to change the time range ofthe calendar view; and in response to receiving the second input,updating the notification region to no longer display the firstnotification when a time range corresponding to the first eventinvitation does not overlap with the changed time range of the calendarview.
 4. The method of claim 1, further comprising displaying on thedisplay device, a numerical representation of notifications associatedwith event invitations.
 5. The method of claim 4, wherein the numericalrepresentation is displayed in a different region of the display devicethan the calendar window.
 6. The method of claim 1, wherein the firstnotification further includes details on attendees related to the firstevent invitation.
 7. The method of claim 1, wherein the visual propertythat visually distinguishes the graphical representations of eventinvitations from graphical representations of events is an outlineformat.
 8. A system comprising: a display device; one or more inputdevices; one or more processors; a storage device with instructionsstored thereon, which when executed by the one or more processors,configure the one or more processors to: display, on the display device,a calendar window that comprises concurrently displaying: a calendarview corresponding to a time range, wherein: the calendar view includesgraphical representations of a plurality of events that include a firstgraphical representation of a first event that has a size thatrepresents the duration of the first event and a second graphicalrepresentation of a second event that has a size that represents theduration of the second event; the calendar view includes graphicalrepresentations of a plurality of event invitations that include a firstgraphical representation of a first event invitation that has a sizethat represents the duration of an event that corresponds to the firstevent invitation and a second graphical representation of a second eventinvitation that has a size that represents the duration of an event thatcorresponds to the second event invitation; and the graphicalrepresentations of the plurality of event invitations share a visualproperty that visually distinguishes the graphical representations ofevent invitations from graphical representations of events; and anotification region, wherein: the notification region includes a firstnotification corresponding to the first event invitation and a secondnotification corresponding to the second event invitation; the firstnotification corresponding to the first event invitation includes anaccept icon for accepting the first event invitation and a decline iconfor declining the first event invitation; and while the calendar view isdisplayed: receive, via the one or more input devices, an input thatcorresponds to selection of the accept icon in the first notification;and in response to the received input, update the calendar view on thedisplay by changing the visual property of the first graphicalrepresentation of the first event invitation to indicate that the eventinvitation has been accepted.
 9. The system of claim 8 wherein thesecond notification includes an accept icon for accepting the secondevent invitation and a decline icon for declining the second eventinvitation; and the one or more processors are further configured to,while the calendar view is displayed, to: receive, via the one or moreinput devices, a second input that corresponds to selection of thedecline icon in the second event invitation; and in response to thereceived second input, update the calendar view on the display byremoving the second graphical representation of the second eventinvitation to indicate that the event invitation has been declined. 10.The system of claim 8, wherein the one or more processors are furtherconfigured to: receive via the one or more input devices a second inputto change the time range of the calendar view; and in response to thereceived second input, update the notification region to no longerdisplay the first notification when a time range corresponding to thefirst event invitation does not overlap with the changed time range ofthe calendar view.
 11. The system of claim 8, the display devicedisplays a numerical representation of notifications associated withevent invitations.
 12. The system of claim 11, wherein the numericalrepresentation is displayed in a different region of the display devicethan the calendar window.
 13. The system of claim 8, wherein the firstnotification further includes details on attendees related to the firstevent invitation.
 14. The system of claim 8, wherein the visual propertythat visually distinguishes the graphical representations of eventinvitations from graphical representations of events is an outlineformat.
 15. A non-transitory computer-readable medium comprisinginstructions, which when executed by one or more processors configurethe one or more processors to perform operations comprising: at acomputing device with a display device and one or more input devices:displaying, on the display device, a calendar window that comprisesconcurrently displaying: a calendar view corresponding to a time range,wherein: the calendar view includes graphical representations of aplurality of events that include a first graphical representation of afirst event that has a size that represents the duration of the firstevent and a second graphical representation of a second event that has asize that represents the duration of the second event; the calendar viewincludes graphical representations of a plurality of event invitationsthat include a first graphical representation of a first eventinvitation that has a size that represents the duration of an event thatcorresponds to the first event invitation and a second graphicalrepresentation of a second event invitation that has a size thatrepresents the duration of an event that corresponds to the second eventinvitation; and the graphical representations of the plurality of eventinvitations share a visual property that visually distinguishes thegraphical representations of event invitations from graphicalrepresentations of events; and a notification region, wherein: thenotification region includes a first notification corresponding to thefirst event invitation and a second notification corresponding to thesecond event invitation; the first notification corresponding to thefirst event invitation includes an accept icon for accepting the firstevent invitation and a decline icon for declining the first eventinvitation; and while displaying the calendar view: receiving, via theone or more input devices, an input that corresponds to selection of theaccept icon in the first notification; and in response to receiving theinput, updating the calendar view on the display by changing the visualproperty of the first graphical representation of the first eventinvitation to indicate that the event invitation has been accepted. 16.The non-transitory computer-readable medium of claim 15 wherein thesecond notification includes an accept icon for accepting the secondevent invitation and a decline icon for declining the second eventinvitation; and while displaying the calendar view, the operationsfurther comprise: receiving, via the one or more input devices, a secondinput that corresponds to selection of the decline icon in the secondevent invitation; and in response to receiving the second input,updating the calendar view on the display by removing the secondgraphical representation of the second event invitation to indicate thatthe event invitation has been declined.
 17. The non-transitorycomputer-readable medium of claim 15, the operations comprising:receiving via the one or more input devices a second input to change thetime range of the calendar view; and In response to receiving the secondinput, updating the notification region to no longer display the firstnotification when a time range corresponding to the first eventinvitation does not overlap with the changed time range of the calendarview.
 18. The non-transitory computer-readable medium of claim 15, theoperations further comprising displaying on the display device, anumerical representation of notifications associated with eventinvitations.
 19. The non-transitory computer-readable medium of claim18, wherein the numerical representation is displayed in a differentregion of the display device than the calendar window.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the firstnotification further includes details on attendees related to the firstevent invitation.